Models for Future Structured Tool State Work #18470
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jmchilton
force-pushed
the
structured_tool_state_models
branch
7 times, most recently
from
a7af2c7
to
638800a
Compare
jmchilton
force-pushed
the
structured_tool_state_models
branch
3 times, most recently
from
513066b
to
a5645e3
Compare
jmchilton
force-pushed
the
structured_tool_state_models
branch
from
a5645e3
to
2457f97
Compare
|
I think tool |
4 tasks
|
The tool state stuff in here is solid - but I've made a bunch of progress on I think a better tool shed 2.0 tool endpoint. I'm going to close this out and stabilize a PR I feel has a rich shed endpoint and a more future facing approach to caching. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"Meta" models describing tool inputs. The downstream work already includes client side validation of tool request and near instant async tool form submission and background job creation based on these models (#17393). Future work will include JSON schema definitions for the internal tool state for the execution of a single job, tool request tool state JSON schema that describes map/reduce operations available in the API that transcend multiple jobs, cleaner and more robust CWL implementations.
This part is the models and test validation framework that verify implementations as well the exposure of these models via the Tool Shed 2.0 API - both as the pydantic meta model description and as the JSON schema for the future tool request API. Future ToolShed 2.0 APIs will include JSON schemas for workflow definitions and tool test cases.
More information on the tool state project can be found at https://docs.google.com/document/d/1HQOLpLN54CjrB-wbD463XqzvUm-dNB8vTXUFBExh_2o/edit?usp=sharing.
How to test the changes?
(Select all options that apply)
License